Central programmed loss and theft prevention

ABSTRACT

The proliferation of networked, wireless-enabled devices is challenged by the reliance upon password management and user knowledge of privacy and security techniques to maintain control over data that is personal, proprietary or restricted. This disclosure enables a geo-proximity security and privacy system for assuring control and non-repudiation for wireless-enabled devices by relying upon location and trusted network relationships among a set of wireless-enabled devices, where one or more devices may act as a control or master key.

RELATED APPLICATIONS

This application is a continuation-in-part of application Ser. No. 15/717,715 filed Sep. 27, 2017, now U.S. Pat. No. 10,028,147 dated Jul. 17, 2018, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 15/331,583, filed Oct. 21, 2016, now U.S. Pat. No. 9,794,789, issued Oct. 17, 2017, which is a continuation of U.S. Non-provisional patent application Ser. No. 14/819,360 filed Aug. 5, 2015, now U.S. Pat. No. 9,503,902, issued Nov. 22, 2016, which is a non-provisional of U.S. Provisional Application No. 62/034,088 filed Aug. 6, 2014, all of which are incorporated herein by this reference.

COPYRIGHT NOTICE

© 2014-2018 Lillie Coney. A portion of the disclosure of this embodiment document contains material, which is subject to copyright protection. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. See 37 CFR § 1.71(d).

TECHNICAL FIELD

This invention pertains to security and more specifically to prevention of loss or theft of wireless-enabled physical objects utilizing wireless communications with a user-programmable central programming device that implements location proximity rules.

BACKGROUND

The proliferation of digital devices and the desire to prevent theft, abuse or misuse of information accessible by a device has imposed a password management regime upon consumers that is challenging their ability to develop and maintain control over wireless-enabled, networked technology. Social and economic dependence upon complex password management by individual consumers who are faced with an exponentially expanding number of consumer wireless-enabled devices is unsustainable.

The next technology wave is fast approaching in the form of the “Internet of things,” where the lives of consumers/workers/citizens will be delinked from fixed geographic locations. The power of digital devices has made work, learning, play, and healthcare services available at any location where a person with the right technology is present. Due to advances in RFID technology, the adoption of Internet Protocol version 6 (“IPV6”), the development of near field communication, continued miniaturization of computing technology, broad and sustained adoption of mobile wireless technology (means of supporting wireless communication), innovations in microchip technology, and software engineering, many consumer and commercial products, appliances and equipment have a unique Internet Protocol address, whereby one device is distinguishable from another. Indeed, IPV6 arises by necessity as the sheer number of addresses outstrips the IPV4 protocol. This proliferation of nodes compounds the security challenges, but at the same time presents opportunities to prevent loss and theft of physical items of all stripes.

SUMMARY

The following is a summary of the present disclosure to provide a basic understanding of some aspects of the disclosure. The summary is not intended to identify key/critical elements of the disclosure or delineate the scope of the disclosure. Its sole purpose is to present some concepts of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.

This disclosure describes methods and apparatuses of a security system for protecting wireless-enabled devices and/or associated data from theft, loss, misuse, and abuse. This goal may be achieved through, but not limited to, the creation of a relationship between or among devices through a link, where the relationship may be associated with the physical proximity of the devices to each other. The methods and apparatuses described may comprise, but are not limited to, the use of a central programming device located within physical proximity of a wireless-enabled device or devices. The central programming device may be utilized to enroll devices and assign relationships between the devices, as well as assign levels of security and corresponding protocol(s) to the devices to be utilized in the case that one or more of the enrolled devices become separated from other enrolled devices within the same linked group.

The central programming device may act as a controller of enrolled devices, which means it can assign links among devices (for example, using Classless Inter-Domain Routing or CIDR) such that the linked devices share a unique access security protocol. The central programming device may be able to, but is not limited to: establishing parameters for device access and use; assigning levels of functionality to linked devices; setting proximity distances that linked devices may be separated from each other without activating the security protocol; and facilitating escalation of the levels of response if distance parameters exceed the set proximity distances. In some examples, the central programming device may be limited to operation at a location where the central programming device was initialized. This limiting of operation provides an additional layer of security to better manage access, use, and functionality of wireless-enabled technology located in a home, office or elsewhere.

In some embodiments, a wireless communication system to prevent loss or theft of physical items may include the following:

a central programming device (“CPD”) having a user interface; and at least one wireless-enabled device capable of wireless communication with the CPD;

the CPD including a processing device and a memory device having instructions stored thereon, wherein the instructions, in response to execution by the processing device, cause the CPD to:

responsive to input via the user interface or preset preferences, identify and register the wireless-enabled device at the CPD as a registered device, the register step including acquiring an IP address of the registered device; establish at least one operating rule for the registered device, responsive to user control or preset preferences, the operating rules including a proximity rule; responsive to input via the user interface or preset preferences, establish a distance value for the proximity rule; responsive to input via the user interface or preset preferences, set an alert format for the registered device; responsive to input via the user interface or preset preferences, set a time parameter rule for the registered device; commence a loss prevention session using wireless communications between the CPD and the registered device; during the loss prevention session, monitor a current distance of the registered device from the CPD, based on data sent to and received from the registered device; and based on a violation of the proximity rule combined with the time parameter rule, conditionally activating an alert using the set alert format.

The central programming device may comprise or have access to a storage unit for storing information related to each linked device, and it may securely transmit stored information based on owner established protocols. The protocols may cause the central programming device to perform actions, including sending information to linked devices to alert an owner or controller of the device, a home/business security service, a friend or a family member, or contact 911 emergency services in response to one or more enrolled device(s) violating proximity relationships or other operational rules.

The central programming device may also assign or delegate controlling functions to a linked device, which configures the linked device to perform specified operations in response to a violation of security protocols. The central programming device may be integrated with home or office security systems, enable automated enrollment and/or generate a log of devices that enter the communicable area (within wireless communication range) of the central programming device. The central programming device may be configured to operate with bar-coded devices readers and other IP enabled technology in appliances or office equipment.

The central programming device may generate white noise in the form of False RFID or simulated wireless communication signals to mask the active communication or presence of wireless-enabled devices within its range. The central programming device may be able to generate, or simulate, wireless communication to a degree necessary to prevent interception of the wireless communication through electronic eavesdropping, thereby supporting privacy and security.

Electronic communications among authorized, linked devices may be enabled when the linked devices are within a physical proximity to the central programming device. In some examples, communication relationships may be established for linked devices even though at least one of the devices is outside the physical proximity to the central programming device or is violating another rule assigned to the linked devices.

The wireless-enabled devices may be managed and monitored securely when outside of the physical proximity of the central programming device. In some examples, the central programming device may communicate with the linked devices while they are outside of the physical proximity.

The central programming device may be able to identify, track, and manage non-wireless-enabled items by tracking an RFID tag, or similarly operating technology, attached to the items. The non-wireless-enabled items may be linked to other items and wireless-enabled devices, and may operate similarly to wireless-enabled devices that have been linked to other wireless-enabled devices.

The central programming device may utilize RFID, internet protocol (IP), near field communication, wi-fi, or any other type of wireless communication now known or later developed to perform the disclosed operations. Further, the central programming device may alternate between communication protocols for communication with devices that require a particular type of communication protocol. For example, if one device requires RFID communication and a second device requires IP communication, the central programming device may be able to utilize the corresponding communication protocol to communicate with both devices.

Additional aspects and advantages of this disclosure will be apparent from the following detailed description, which proceeds with reference to the accompanying drawings.

BRIEF DESCRIPTIONS OF THE DRAWINGS

FIG. 1 illustrates an example network comprising a central programming device.

FIG. 2 illustrates an example network comprising defining objects forming a geo-proximity fence.

FIG. 3 illustrates an example network comprising linked devices.

FIG. 4 illustrates an example network comprising a first token and a second token.

FIG. 5 illustrates an example network tracking objects entering a geo-proximity fence associated with a token.

FIG. 6 is a flow chart illustrating a process for linking devices.

FIG. 7 is a flow chart illustrating the process of monitoring a group of linked devices.

DETAILED DESCRIPTION

The systems and methods disclosed utilize an application of technology and security protocols to provide security for wireless-enabled devices among home, office, public, and other settings. One advantage of this innovative approach of the disclosed systems and methods is a reduction in the quantity of passwords and personal identification numbers (PINs) that are required for users to access the wireless-enabled devices included within the systems and methods. The systems and methods disclosed may ensure that only users with authorization can access, use, or control the devices within the system or method.

FIG. 1 illustrates an example network comprising a central programming device 104. Central programming device 104 may be either fixed at a location or mobile, allowing the central programming device 104 to be moved to a desired location of operation of the example network. In examples where the central programming device 104 is mobile, the central programming device 104 may be configured only to operate within an area, such as within geo-proximity fence 102.

Central programming device 104 may be wireless-enabled, allowing the central programming device 104 to communicate with other wireless-enabled devices and allowing tracking of the devices and objects that are within the central programming device's 104 range of communication. Central programming device 104 may communicate with other wireless-enabled devices using multiple diverse types of wireless communication, including any of IP, RFID, Wi-Fi, Bluetooth, near field communication, and similar communication protocols. The central programming device may further be able to determine locations of wireless-enabled devices through use of GPS, location determining systems set up within structures, RFID, Wi-Fi, Bluetooth, near field communication, or a combination thereof.

In some examples, devices that are not wireless-enabled may be converted into a wireless-enabled device through use of geo-proximity plugs. The geo-proximity plugs may be a device or object that can be connected to a device that is not wireless-enabled and, thereby, allowing the device to communicate or be recognized by the central programming device 104 and other wireless-enabled devices. The geo-proximity plugs may be discrete and not easily removed. In some examples, removal of the geo-proximity plugs may require authorization, such as through entry of a pass code, biometric certification, authorized access to the central programming device 104 to generate a removal request, or similar authorization techniques. An alert may be generated in response to unauthorized removal of a geo-proximity plug, allowing for correction of the unauthorized removal.

One example of a geo-proximity plug is by placement of an RFID tag on the device or object that is not wireless-enabled. The central programming device 104 may be configured to read RFID tags, allowing the central programming device 104 to identify any object that enters the central programming device's 104 range of communication. The RFID technology may be either encrypted or unencrypted technology.

Central programming device 104 may be configured to generate relational links between wireless-enabled devices and define rules associated with the relational links. The relational links and associated rules may define how the central programming device 104 and the linked devices operate in certain situations. In some embodiments, a relational database may be utilized, wherein the relational database stores all of the relational links and associated rules within a network.

In some examples, the relational links may be generated by a user interacting with the central programming device 104 to create a relational link between a plurality of wireless-enabled devices, such as first linked device 106 and second linked device 108. The rules associated with the relational link among the devices may be generated by the central programming device 104, the first linked device 106 or the second linked device 108, or any combination thereof. The rules may be editable by an authorized user.

In some examples, the central programming device 104 will be able to generate relational links automatically. For example, upon initialization the central programming device 104 may detect all wireless-enabled devices within its communication area and dynamically generate rules based on tracking the locations and operations of the detected devices. The central programming device 104 may be configured to track the locations and operations of the wireless-enabled devices for a selected period of time and then generate relational links and associated rules corresponding with the results of the tracking during that time period.

Further, relational links among the central programming device 104 and other linked devices may be generated based on default designations stored on one or more of the linked devices, such as first linked device 106 and second linked device 108, indicating that a relational link should be generated. The first linked device 106 may store a designation indicating that the first linked device 106 should be relationally linked to the second linked device 108. The designation may be placed on the first linked device 106 by a manufacturer of the first linked device 106, by software operating on the first linked device 106, by an operating system operating on the first linked device 106, through a network connection with the first linked device 106, or any combination thereof.

In response to the central programming device 104 detecting the first linked device 106 with the stored designation, the central programming device 104 may automatically generate a relational link between the first linked device 106 and the second linked device 108 based on the designation. In other examples, in response to detecting the first linked device 106 with the stored designation, the central programming device 104 may trigger a prompt querying whether the user wants the relational link indicated by the stored designation to be generated. The central programming device 104 will either generate the relational link of the designation or suppress the generation of the relational link of the designation based on the response of the user.

As devices are assigned relational links, the central programming device 104 may collect information regarding the devices being assigned the relational links. Some of the information that may be collected regarding the devices being assigned the relational links may include description, designation, name, intended location, current location, communication originating from the devices, or any combination thereof. This information may allow the central programming device 104 to identify the linked devices. In response to being assigned a relational link, the linked devices may each be assigned a distinct token address, enabling identification and communication with a specific linked device. The central programming device 104 may continue to collect information associated with the linked devices while they reside in the communication area of the central programming device 104. This information may be added to the database mentioned above.

Once relational links are generated, a group of linked devices, such as first linked device 106 and second linked device 108, and the central programming device 104 may be configured to communicate among each other, as illustrated by communication lines 112, 114, and 116. For example, the first linked device 106 may be configured to access data stored on the central programming device 104, the second linked device 108, or both.

Non-linked devices, such a non-linked device 110, may be prevented from communicating with the central programming device 104 and the group of linked devices. In some examples, the central programming device 104 and the group of linked devices may embed communication among themselves with additional, random bits, thereby preventing identification of the embedded communication without the receiving device having proper decoding information. The group of linked devices may be provided with the proper decoding information for identifying the embedded communication, whereas the non-linked device 110 may not be provided proper decoding information.

Central programming device 104 may further be configured to prevent the non-linked device 110 from recognizing that the group of linked devices and the central programming device 104 exist or that the central programming device 104 and the group of linked devices are communicating among themselves. In some examples, an alert may be generated in response to the non-linked device 110 entering the geo-proximity fence 102.

The central programming device 104 may generate a plurality of relational links, where each relational link may be associated with distinct groups of devices with each relational link having rules associated with the relational link. For example, the first linked device 106 may belong to a group of linked devices that, in response to violating an associated rule, will cause the first linked device 106 to limit access to certain functionality of the device, whereas the second linked device 108 may belong to a second group of linked devices that, in response to violating an associated rule, will lock all functionality of the device and prevent all users from accessing the device.

The rules associated with the relational links may be requested by a user of the proximity-based system or by default designations stored on one or more of the linked devices, such as first linked device 106 and second linked device 108. The user may generate a request for the rule on the central programming device 104, on any of the linked device, or any combination thereof.

The designations may indicate a rule should be associated with one or more of the linked devices. For example, the first linked device 106 may have a stored designation indicating that a rule should be defined where the first linked device 106 should be within a certain distance of the second linked device 108. The central programming device 104 may define the rule in response either to detecting the first linked device 106 or in response to detecting a relational link being generated between the first linked device 106 and the second linked device 108. In some examples, the central programming device 104 may query a user to determine whether the rule should be defined. The central programming device 104 would either define the rule or not define the rule based on the response of the user to the query.

The central programming device 104 may define rules based on tracking selected wireless-enabled devices associated by a relational link. The central programming device 104 may track the locations and operations of the selected devices and define a rule for the group of selected devices corresponding to the results of the tracking. The central programming device 104 may be configured to identify when the selected devices have violated a defined rule and determine whether to alter the rule or take remedial action, such as generating an alert, based on any of the tracking data the central programming device 104 has acquired or the severity of the violation.

An example of a rule that may be associated with a group of linked devices involves generating a geo-proximity fence 102 around the central programming device 104, such as geo-proximity fence 102. While geo-proximity fence 102 is illustrated as a circular area, it will be understood that geo-proximity fence 102 may comprise any shape and may be defined in either or both horizontal and vertical directions. For example, the geo-proximity fence 102 may be configured to exist with its border along the perimeter of the house, such that the area inside the house is inside the geo-proximity fence 102 and the area outside the house is outside the geo-proximity fence 102. In institutional examples, such as businesses, schools, or government buildings, the geo-proximity fence 102 may be configured to have its border along the perimeter of the institutional building, or may be limited to a portion of the institutional building, thereby allowing multiple agencies or entities to exist in one building while still securing their information from other agencies or entities in the same building.

Another example of a rule that may be associated with a group of linked devices involves defining the borders of the geo-proximity fence 102 in relation to the group of linked devices. For example, the geo-proximity fence 102 may have a border defined as a certain distance from one of the linked devices, such as the first linked device 106, within the group. It may then be determined whether the rest of the linked devices within the group are inside or outside the geo-proximity fence 102 depending on the distance of the linked devices from the first linked device 106.

A rule may define the borders of the geo-proximity fence 102 as a certain fixed area that may not include the central programming device 104 within the borders of the geo-proximity fence 102. The geo-proximity fence 102 may then be able to define a certain area as the geo-proximity fence 102, irrespective of the current locations of the central programming device 104 and the linked devices.

The borders of the geo-proximity fence 102 may be defined based on a location identifier, such as an address of a building, a name of a location or area, any other identifying label or characteristic, or any combination thereof. A user may enter the location identifier into any of the central programming device 104 or linked devices along with a request that the borders of the geo-proximity fence 102 be defined based on the building, location, area, or combination thereof, associated with the location identifier. The central programming device 104 or any of the linked devices may access a database, such as an electronic phone book or electronic maps, and set the borders of the geo-proximity fence 102 based on spatial data retrieved from the database.

The borders of the geo-proximity fence 102 may alternatively be based on a map or floorplan illustrating the desired location of the geo-proximity fence 102. The map or floorplan may be displayed to the user on one or both of the central programming device 104 and the linked devices. The user may indicate an area on the displayed map or floor plan which the user desires the borders to encompass. The indication of the area may include an indication of a room, a building, an area encompassed by rectangle or other shape generated by the user on the display of the map or floor plan, or any combination thereof. In response to the indication, the central programming device 104 may set the borders of the geo-proximity fence 102 to encompass the indicated area.

In some examples, the border of the geo-proximity fence 102 may be defined by physically moving the central programming device 104 to different locations and indicating on the central programming device 104 that the current location is intended to be a border of the geo-proximity fence 102. The border of geo-proximity fence 102 may be defined by entering coordinates or distances from an object, such as the central programming device 104, in either or both of the horizontal and vertical directions at which the border of geo-proximity fence 102 should be defined.

The border of the geo-proximity fence may also be defined by objects, such as defining objects 202, 204, 206, 208 illustrated in FIG. 2. As the defining objects 202, 204, 206, 208 move locations, the borders of the geo-proximity fence 210 may change correspondingly, thereby creating a type of boundary fencing. The objects 202, 204, 206, 208 may comprise wireless-enabled devices, objects labeled with RFID tags, or other objects that the central programming device 104 may sense the object position. Further, the defining objects 202, 204, 206, 208 may comprise devices that are not wireless-enabled, but have a geo-proximity plug, as discussed throughout this application, attached to the devices that allows the central programming device 104 to determine a location of the devices.

In some examples, a portion of the geo-proximity fence 210 may be defined by the defining objects 202, 204, 206, 208 and another portion may be defined in another manner. For example, the defining objects 202, 204, 206, 208 may define the border of the geo-proximity fence 210 in the horizontal direction, while the central programming device 104 may define the border of the geo-proximity fence 210 in the vertical direction.

Further, certain areas within a defined border of geo-proximity fence, such as geo-proximity fence 102 (FIG. 1) or geo-proximity fence 210 (FIG. 2), may be defined and labeled. For example, when the defined border of the geo-proximity fence encompasses a house, areas encompassed by each of the rooms within the house may be defined and labeled. The central programming device 104 or linked devices may define an area encompassed by the room by accessing a floor plan of the house from a database or receiving spatial parameters from a user. The central programming device 104 may further label the area with a label included in the floor plan or a label provided by the user. Accordingly, an area encompassed by a border of a geo-proximity fence may be further partitioned into one or more defined areas recognized by either or both central programming device 104 and the linked devices.

The central programming device 104, the linked devices within a group, or a combination of both may be configured to perform operations in response to violation of any of the rules associated with the relational links of the group. The operations may be suppressed by excusing a violation of any or all of the rules.

In response to a violation of any of the rules, an alert may be generated by the central programming device 104 or one of the linked devices in the group indicating that a rule has been violated. In some examples, the alert may include an identification of which rule has been violated. The alert may be transmitted to the central programming device 104, the linked devices in the group that did not violate the rule, or any combination thereof and the alert may be displayed on the device. In some examples, the alert may be transmitted to an electronic device outside of the linked devices, such as an electronic device associated with emergency service providers or other service providers.

The alert may be suppressed by excusing the violation of a rule either prior to the violation or in response to receiving an alert of the violation. For example, the central programming device 104 may receive an indication that the first linked device 106 is being removed from the area of the geo-proximity fence 102 and that an alert should not be generated. Proof of authorization, such as entering of a pass code or satisfying another relational link rule, may be required to indicate that an alert should not be generated in response to a violation of a rule.

The alert may further identify a location of the device that violated the rule. The identified location may help to rectify the violation. For example, if a linked device, such as first linked device 106, leaves the area enclosed by geo-proximity fence 102, a user may be able to locate the first linked device 106 and move the first linked device 106 back to within the geo-proximity fence 102. Identification of the location may also assist a user in identifying theft of any of the linked devices and recovering the stolen device.

In some examples, a linked device that violates a rule may be configured to either lock access to the linked device or provide limited functionality of the device. For example, in response to first linked device 106 being outside the area of geo-proximity fence 102, first linked device 106 may prevent a user of the first linked device 106 from accessing information stored on the central programming device 104. In some examples, a violation of a rule may lock access or provide limited functionality to a portion of the linked devices, all of the linked devices, the central programming device 104, or any combination thereof.

In response to violation of a rule, central programming device 104 may be configured to initiate a request to a third party or the linked devices to perform or not perform an action. For example, where a set of keys and a bank card have been assigned a relational link with a rule that both the set of keys and bank card should be within geo-proximity fence 102 for the bank card to complete a credit charge, if the set of keys are not within the geo-proximity fence 102 when a credit charge is attempted with the bank charge, a request may be sent to the bank to limit the purchases to a maximum value of twenty dollars.

In some examples, a linked device that violates a rule may be configured to display a message on the device in response to the violation of the rule. For example, the linked device may display “out of use area,” “stolen,” “lost property of ‘user's name,’” or any combination thereof in response to the violation. In some examples, a transparent decal may be placed on the linked device, which appears transparent when the linked device is not violating any rules and displays a message when the linked device is violating a rule.

In some examples, a rule for a group of linked devices may allow access to information, a device, or a secured location in response to the rule being satisfied. For example, a user's cell phone and key may be linked in a group and, when the linked devices satisfy a rule of being within a certain distance of each other and a vehicle, access may be granted to the vehicle and the vehicle may be operated. In response to the rule being violated, access to the vehicle may be denied and the car may not be operated. In a further example, the vehicle may be equipped with a vehicle security system, such as Onstar, that may further authenticate the operator and, in response to failed authentication, may prevent operation of the vehicle and initiate an alert to a third party, such as customer service of the vehicle security system or law enforcement, that improper access has been gained to the vehicle. A rule may grant or restrict access to vehicles, computing systems, computing devices, telecommunications equipment, household appliances, office equipment, entry doors, elevators, operation of heavy equipment, and other areas or objects where authorization is desired for access.

In examples where greater security is desired, an activation key code, a pass code, biometric data, or any combination thereof may be added as an additional layer of protection. The activation key code or pass code may be desired where the information or area being accessed is highly sensitive. Examples where an activation key code or pass code may be desired includes healthcare information, governmental information, workstations containing information vital to commercial interests, and locations and information having great monetary value.

In some examples, the central programming device 104 may store certain information that may be accessible by a wireless-enabled device through remote access without requiring the device to have a relational link with the central programming device. Access may be gained through proof of authority to access through various authentication techniques such as entry of a pass code, biometric data, 2FA, etc. This type of access may allow a user to access data related to product enrollment when shopping, thereby improving the efficiency of the process of restocking items that are needed and avoiding over purchasing of items already identified as being within a geo-proximity fence associated with the user.

Further, the wireless-enabled device with remote access may be configured to request generation of relational links, request definition of rules associated with the relational links, request modification of any existing relational links or rules, or any combination thereof from a remote location. For example, a user on vacation may access the central programming device 104 through the wireless-enabled device with remote access and request a rule be modified to require higher security measures for access to a secure location or to prevent access to the secure location. This may allow a user to increase security measures while away from the proximity-based system.

A rule may be assigned that initiates an operation upon entry or exit of a linked device into the geo-proximity fence 102. In some examples, the rest of the linked devices and the central programming device 104 may be required to be within the geo-proximity fence 102 for the operation to initiate in response to the entry or exit of the linked device. Some examples of the operations that may be initiated include calling an elevator, turning on the lights in a room, and turning off the lights in a room.

In some examples, once of a violation of a rule has been rectified such that no rules are being violated, the network may automatically transition to a state of operation associated with all the rules being satisfied. For example, if first linked device 106 was outside geo-proximity fence 102 which resulted in violation of a rule preventing access to the device, once the first linked device reentered the geo-proximity fence 102 the first linked device may automatically regain full functionality. In other examples, a pass code entry may be required before regaining full functionality after rectifying all rule violations.

FIG. 3 illustrates an example network comprising linked devices. In this example network, there may be no central programming device 104 (FIG. 1) or the central programming device 104 may not be part of the linked group. In this network, one of the linked devices, such as first linked device 304 may act as a token performing the operations of the central programming device 104 (FIG. 1). In some examples, the token may perform the monitoring operations of the central programming device 104 (FIG. 1) and a central programming device 316 separate from the linked group may perform the operations of assigning the web-enabled devices with relational links, defining rules for the group of linked devices, or any combination thereof. The token may be configured to perform any portion of the operations performed by central programming device 104 (FIG. 1) and the remainder of the operations may be performed by central programming device 316.

The token may comprise an object associated with a root authorization (subnet) address that may support stationary architectures, mobile architectures, or both. A token assignment may be generated by the central programming device 316. The token may be able to collect information from the linked devices and store the information for later access or use the information to perform operations, such as tracking the linked devices and determining if a rule is satisfied.

Geo-proximity fence 302 may be defined in relation to the first linked device 304 operating as a token. For example, the border of geo-proximity fence 302 may be set to a certain distance from first linked device 304. In the example situation, second linked device 306 and third linked device 308 may be required to be within the border of geo-proximity fence 302 to satisfy a defined rule. In some examples, the second linked device 306 and the third linked device 308 may be configured to function minimally or not at all when the devices are outside of geo-proximity fence 302. Upon reentry into the border of geo-proximity fence 302, the second linked device 306 and the third linked device 308 may automatically return to normal operation or may require entry of a pass code to return to normal operation upon reentry.

FIG. 4 illustrates an example network comprising a first token 412 and a second token 422. A network may be configured to have multiple tokens. Each token may be assigned relational links to a group of wireless-enabled devices. The group of wireless-enabled devices assigned to a token may comprise devices that are not relationally linked with any other token or the devices may share relational links with multiple tokens.

Where multiple tokens have been assigned, the token and group of associated wireless-enabled devices may be utilized to identify a user associated with the token. First token 412, first linked device 414, and second linked device 416 may comprise a first linked group associated with a first user 410, whereas second token 422, third linked device 424, and fourth linked device 426 may comprise a second linked group associated with a second user 420. In examples where the linked group may provide access to secured data or a location, it may be determined which user is gaining access based on which group of linked devices was satisfying the rule allowing access at the time access was granted.

In some examples, central programming device 402 may determine which user was granted access to the secured data or location. The central programming device 402 may generate a log of users who accessed the secured data or location. The log may be reviewed later to determine who accessed the secured data or location at a given time and may be used to determine who performed an unauthorized activity.

In networks configured for multiple tokens, a master account option may exist allowing control over rules, relational links, information, or any combination thereof associated with all, or a portion, of the tokens. The master account option may allow the central programming device 402 to act as an administrator granting or denying access to a token associated with a particular user.

Any of the examples disclosed may allow the central programming device to be physically reset. The physical reset may operate to reset the relational links, the rules associated with the relational links, the assignment of tokens, or any combination thereof. The physical reset may be useful where a user has forgotten a pass code for access to the central programming device or would like to start fresh in generating the relational links.

In response to the physical reset, central programming device may allow a selection of several options. These options may comprise ending the geo-proximity lock, removing the token and making the central programming device the token, allowing another linked device to serve as the token, allowing two or more devices to pair as a field that allows their use while outside of the geo-proximity location, or any combination thereof.

FIG. 5 illustrates an example network tracking objects entering a geo-proximity fence 502 associated with a token 504. Token 504 may have relational links with wireless-enabled devices, such as first linked device 506 and second linked device 508. In some examples, token 504 may be configured to track objects entering and exiting the geo-proximity fence 502 when all rules associated with group of linked objects are satisfied and configured not to track the objects when any of the rules are being violated.

First object 510 and second object 512 may be moved into and out of the geo-proximity fence 502. Both the first object 510 and the second object 512 may be assigned distinct token addresses upon entry into the geo-proximity fence 502. The token addresses may be used for tracking the first object 510 and the second object 512 while each is located within the geo-proximity fence 502.

Alerts may be generated in response to any of the objects entering or exiting the geo-proximity fence 502. For example, the first object 510 enters the geo-proximity fence 502. In response to entering the geo-proximity fence, information associated with the first object 510 may be captured or recorded by the token 504 and an alert may be generated indicating a new object has entered the geo-proximity fence 502. The second object 512 exits the geo-proximity fence 502. In response to exiting the geo-proximity fence 502, information associated with the second object may be captured or recorded and an alert may be generated indicating the second object 512 exited the geo-proximity fence 502.

While in the geo-proximity fence 502, the first object 510 and the second object 512 may be tracked. A record of the objects within the geo-proximity fence 502 may be maintained and accessed. One example where the record may be useful is when a user is trying to determine whether a particular bathroom, enabled with a geo-proximity fence 502, has hand soap and the amount of hand soap that is present. Information, such as location, state, or any combination thereof of an object, may be gathered while the object is within the geo-proximity fence 502. This data may be stored in a database.

In some examples, a third party, such as retailers, wholesalers, and manufacturers may provide information about an object. For example, a retailer may provide an expiration date associated with a carton of milk. Upon entry of the carton of milk into the geo-proximity fence, a reminder may be generated for the expiration date and an alert may be generated if the carton of milk remains in the geo-proximity fence 502 past the expiration date.

Further, the information about the object may include a purpose or a function of the object. A user may also be able to define the purpose or function of the object if not included in the information, or may alter the purpose or function of the object acquired from the information.

The proximity-based system may determine an expected location of the object based on the purpose or function of the object. For example, the object may be toothpaste, which has a defined function of being used for brushing teeth, and, accordingly will have an expected location of being within a defined bathroom partition of the geo-proximity fence 502 associated with a user brushing his teeth.

In some examples, the user may define an expected location corresponding to the purpose or function of the object. The proximity-based system may then be able to determine the expected location of the object based on the purpose or function of the object and the user-defined expected location corresponding to the purpose or function.

In response to detecting that an object is outside of its expected location, the proximity-based system may generate an alert on any, or a combination, of the central processing device, token, or linked devices indicating the object should be returned to its expected location. A user may then return the object to the expected position causing the alert to cease or the user may excuse the alert, thereby ceasing the alert.

In some examples, the user may request indication of a location of a certain object. The user may input a label associated with the certain object into any, or a combination, of the central processing device or linked devices and request from the proximity-based system an indication of the location of the certain object. In response, the proximity-based system may return the location of the certain object based on tracking of the object by the proximity-based system. In examples where the proximity-based system has not been tracking or is unable to access tracking information concerning the object for some reason, the proximity-based system may return the expected location based on the purpose or function of the object. The location may then be displayed to the user on the device generating the request for the indication of the location.

One method of tracking objects is through passive radio frequency identification (RFID) technology. The central programming device, token, or both may incorporate RFID tag reading capability. RFID tags may be placed on objects, thereby allowing identification of the object. Any object labeled with an RFID tag may perform some of the same functions as the wireless-enabled devices discussed throughout this specification. The RFID tags may contain information regarding the object, which may be read by the central programming device or the token. The central programming device, the token, or both may be configured to link with commercially available RFID readers to allow upload of data to the central programming device or the token.

RFID tags may allow objects brought into the geo-proximity fence 502 to have their locations mapped. The RFID tags may communicate information associated with an object. The information may include when an object is discarded or when expiration dates are exceeded. An alert may be generated in response to the discarding or the expiration date being exceeded.

The RFID tag may contain information allowing the object to be matched with objects within a directory of RFID consumer product information, making the process or enrollment of the object when entering the geo-proximity fence 502 easier. In some examples, a directory of manufacturer skew codes may be stored or accessible by a central programming device also simplifying the process or enrollment of an object entering the geo-proximity fence 502.

The network, when linked to items such as the RFID and SKU codes on wrappers, containers for food or appliances, may manage product use and consumption life cycle of an object. Reports may be generated from the measured product use and consumption life cycle of an object. Further, it may be pre-determined which object would be of such importance that reminders are required to be sent to prompt for replacement of the discarded object.

The central programming device or token may be configured to gather and store all information and data obtained during operation, including information and data related to the linked devices and the objects. The information and data may be analyzed and used to generate reports that may be used for such things as determining consumption of the objects, use of the linked devices and the objects, and movement of the linked devices and the objects. In some examples, the central programming device or token may be configured to analyze a selected portion of the gathered information and data. The gathering and storing of the information and data may be beneficial in accounting of consumable goods, determining depreciation of equipment, and determining what equipment is used, how often the equipment is used, how the equipment is used, and where the equipment is used. Routines may be identified from the analyzed information and data, and the network configuration may be optimized based on the identified routines.

In some examples, the stored information and data regarding enrollment, removal of items, and changes in token status or assignments may be retained unless an authorized request is received. The authorized request may be required to be initiated by a specific central programming device or token, or by a user with an authorized pass code. The request may indicate which portions of the stored information and data should be erased, while the non-indicated information and data is retained. This indication may be beneficial in managing consumables, such as food, cleaning supplies, equipment, and clothing, while allowing a user to erase sensitive, personal or proprietary information.

FIG. 6 is a flow chart illustrating the process of generating a group of linked devices. Step 602 begins by enrolling a wireless-enabled device. The process of enrolling a device may comprise communicating with the wireless-enabled device and assigning the wireless-enabled device a unique address, such as a unique IPV6 address.

Step 604 generates a relational link between the enrolled wireless-enabled device and a group of one or more other devices. Step 606 checks if there are more wireless-enabled devices to be enrolled and repeats steps 602 and 604 for the new device. Once enrolling of the devices has been completed, one or more rules may be assigned to each group of linked devices in step 608. Step 608 may include the process of generating a geo-proximity fence if necessary to enforce the rule. Every relational link within a group of devices is dynamic such that a new wireless-enabled device can be added to a group of linked devices by repeating the process at any time.

Some additional illustrative examples of rules may include the following. Rules Type 1 for Secure Access Control:

In this example, access to a particular work computer is controlled. For this purpose, multiple wireless-enabled devices may be linked. For example, a company-issued mobile device like a smartphone may associated with the work computer. In addition, a user's company-issued wireless-enabled ID Badge (NFC, BT, pin-chip, etc.) may be associated with the work computer.

The computer to be secured may be linked to the smartphone; conversely, the smartphone may be assigned to that specific computer. Rules may be implemented in various combinations. In one example, the computer is the control device for the smartphone, and the smartphone is the control for the ID Badge. In other cases, the ID Badge may be enabled or operable only while within a predetermined physical proximity of the smartphone. Any device may be required to be present to enable any other device. Two or more devices may be grouped as described so than each one is locked without the other(s) present (within proximity range). A range of access purposes for an office can be enabled using the smartphone and ID Badge when paired with another device or item. For example, a Rule may Control access to a copier while also assigning the copies made to a log.

Another configuration may rely upon metadata that is stored using block chain or another technique that ensures that relational data regarding the data traffic among linked devices can be used to authenticate one or more linked devices. For example, the metadata for a smartphone that is collected over time may store data using block chain to protect against alteration or deletion. If a smartphone is lost, but is later returned, the history of the device's metadata that is secured by block chain can be accessed to authenticate the smartphone.

Another Rule may limit the distance that one device can physically be from the other for the two to function as a component of a key. For example, my ID Badge, only while sufficiently close to my smartphone, may enable unlocking or operating a motor vehicle.

Rules Type 2 Mapping an Area for Tracking Items.

Step 1—Create a virtual boundary using programmable tags that are assigned to a central programming unit.

Step 2—Tags are assigned a name that could be an area: living room, den, bedroom master, bedroom children, bathroom etc.

Step 3—place tags—tags with the same address e.g. master bedroom.

Step 4—items in proximity of the addressed tags are catalogued as being in that address location.

Step 5—Items in each location can be tagged with unique information.

Finding keys with an existing item identifier or one created by the user. The keyring is logged by the programming unit.

The user asks the system where the keys are. Based on the address spaces in the area and the tag nearest the keyring the information is provided. “Couch living room.”

Rules Type—3—

The “one foot rule” for small, tagged items linked to a mobile device. An umbrella is linked to a mobile digital device. The rule is 1 foot and if broken the sound of thunder communicates that the umbrella is outside of the rule. In other words, the user is about to leave the umbrella in the restaurant or elsewhere. Loss is prevented. If the control device is a smartphone and it was being left, it can trigger a “please don't leave me” message in the user's pre-recorded voice, or similar alert.

FIG. 7 is a flow chart illustrating the process of monitoring a group of linked devices. At step 702, a central programming device or token queries a group of linked devices for their current status. The queries may be continuously performed, performed at specified intervals, performed upon request, or any combination thereof. Status information may include, but is not limited to, the location of the queried device, current operation of the device, historical operation of the device, and a log of operators who have accessed the device.

In step 704, the central programming device or token determines whether a rule has been violated based on the status information. If no rule has been violated, the flow returns to step 702 and continues querying the linked devices. If a rule has been violated, the flow continues to step 706 where the central programming device or the token determines if the violation has been excused. If the violation has been excused, the flow returns to step 702 and continues querying the linked devices.

If a rule has been violated and the violation has not been excused, the flow continues to step 708 where the central programming device or the token performs remedial operations. The remedial operations may comprise any one or a combination of the operations discussed above in response to a violation, including generating an alert.

The flow continues to step 710 where the current status of the linked devices is queried. In step 712, the central programming device or the token determines if the violation has been rectified. If the violation has not been rectified, the flow will return to step 706, wherein the network will again check if the violation has been excused after the remedial operations have been performed. If the violation has been rectified, the flow will continue to step 714 where the group of linked devices and the central programming device or token will reenter normal operation.

Computing and device security relies too often on keeping an intruder out and not enough on addressing security should an intruder breach a device or network. This disclosure describes an approach to security computing devices that develops the equivalent of an immune system for computing devices and networks. To meet the challenges to security posed by Internet of Things (IoT) environment requires the active participation of networked devices working in concert to maintain security of devices and systems by sensing the environment for anomalous activity, know threats, and digital hazards analogous to biological immune systems.

The basics of any computing device or computing network “immune system” is a library of known threats that are inherent or learned, and the ability to recognize one or more of them and use the stored responses to these threats to launch countermeasures or defenses that will immobilize or defeat a threat. A second important feature of an autoimmune system is the ability to monitor the environment for healthy functions and processes and readily identify something that is not routine or a threat indicator.

A third important feature is recognition of an unknown or heretofore unidentified or inexperienced threat, the ability to initiate a set of protocols and processes to assess the threat, decision making regarding the potential threat, monitor the behavior and assess this based on previous threats. Such processes may further include, query known data on threats for similar behavior, determine the appropriate level of response to the threat, alert other central programming devices of the new encounter to determine if they have relevant data, monitor the threat for engagement with key systems that are core to the functioning of a device, linkage of devices, central programming functions and/or functionality. Addressing the perceived threat may further include determine the purpose of the threat, tag the file, folder, or device(s) to append to a log, track activity associated with tagged files, folder, or device(s) for indicators of a threat.

Some indicators of a threat may include, e.g., attempts to access mail application, operating system(s), central programming device, customer databases, financial records, payment systems, medical systems, health care applications, industrial control systems, emergency systems, transportation systems, critical infrastructure, defense systems, linked devices, or data contained therein, attempts to access or monitor peripheral devices such as printers, copiers, fax machines, searches of IP addresses, names of people, technology associated with personnel (phone numbers, extensions cellphones, Fitbits, etc. that are associated with people or functions or units within an organization such as accounting, security finance, executive offices, etc.).

The immune system should execute or coordinate a response, for example, implement countermeasures to mitigate or illuminate the threat, assess the effectiveness of countermeasure, monitor the response to the countermeasures, learn form responses, if the countermeasures are not effective, engage protocols that are intended to increase responsiveness of the system.

Some countermeasures may include launch measures to isolate the impact to a single or few device(s), linked devices or network(s) to prevent spread of the threat, assessing the level of risk to other systems, alerting the system regarding the threat, following protocols that minimize risks to the system, implement protocols to assure a level of functionality to allow the system the ability to make decisions on what functions are essential and which are not essential provide resources to sustain essential systems and generate alerts to users to the threat.

In one embodiment, the central programing device(s) may in real time share its experience with fighting an active threat with other central programming device libraries, which may adjust tactics to addressing a similar threat. Further, other central programming devices may offer solutions to the central programing device dealing with a threat to reach as solution to the threat. Central programming devices may be based upon the information received from a central programming devices under threat may modify the level of trust regarding that central programming device, conduct its assessment of the threat's potential to itself based upon factors that may include the type of system under threat, the purpose of the linked devices either singularly or as a whole e.g. financial institution, hospital or school etc., the type of devices or applications threatened, and the type of threat (encryption files systems (type if determined) or gaining access to certain files (if determined), live human guided attacked or automated attack (botnet(s)).

Preferably, the system should record the behaviors of a threat to develop new signatures that may be stored in the database of known threats to inform the system on its characteristics and behaviors so that it can be defeated or contained if revisits the system.

Components of the system may contain, but may not be limited to, a Central Programing Device as described earlier, that governs the gatekeeping function for a set of wireless devices that are linked (“linked devices”) for the purpose of supporting the flow of information among devices sharing a network relationship. The central programming devices may manage a library of known threats, enrollment, and authentication as well as monitoring and management of wireless devices that are linked. It may choose to enroll new devices, or expel others from the system.

Authentication processes may utilize a binary process to determine that trustworthiness of a devices, or a factors-based approach where trust is conditional and may be temporal in nature, which allows trust to be conditional based on factors not inherent to the device or the user.

The security described may allow the central programming devices to have a resident library of wireless technologies that allow the user to designate certain classes of technology to have a set level of trust that does not change regardless of the source of the technology, who may hold the technology. For example, an architectural firm may want to restrict the functionality of digital cameras, while a news organization would want all cameras functioning.

The security as described may be used in large venues like amusement parks where parents and park managers may want to manage the safety and wellbeing of children in the environment. For example, a child may have a water proof wrist device provided for the period their family will be visiting the amusement park. The child's proximity to their parents is set and confirmed by parents—each parent has a unique identity link with their child's wrist band and perimeters for distance take into consideration distance from each parent's linked device. The amusement parks' tracking and monitoring system is seamless and unobtrusive. An animated character may be used as an avatar to engage the child should they be at risk of moving too far from one or both parents. The avatar may automatically engage with visual and audio applications to guide the child back to an acceptable distance. If the wrist ban is broken or removed the Park's alert system can mimic an Amber Alert protocol that may use the child's image in a localized alert or a Park wide alert. Further, parents and Park security can be guided turn by turn to the last known location of the child. Security features may trigger other security measures to reduce the risk of injury or loss of a child.

Wireless devices may be enrolled as trusted devices and the data they process may be treated as trusted or untrusted. A device may function within a defined space, which may be limited to a geo-proximity fence; or a CPD may include or exclude devices based on a range of parameters that may be determined by users, automation, alerts issued by a third party or other factors suited the preferences of the owner/controllers of a system. The complement of central programing device(s) and linked devices working in concert to form a security communication network may be referred to as a fog security network.

In some embodiments, a central programming device may be able to, access a library of known computer device or network attack signatures and compare stored data to files, software, device or application behavior to known attacks to determine whether the current state of a device or application's operation exhibits signs of a threat. The central programing device may adjust the level of trust for a linked device based on device rules, state of operation of the device, behavior of the device or other parameters as determined by the user or automated procedures established by the central programming device, which can alert authority/owner of the network of status changes among linked devices.

Further, the central programming device may server as the manager of tactics and protocols for determining the health status of a device, application, file, or set of files or some combination thereof for diagnosing, and resolution of a threat to linked device operations. In addition, the central programming device may assign roles for linked devices to assure that the underlying function of linked devices is maintained, which may include assigning processing and protocol operations for a device to external linked resources to meet the underlying objective of a critical component as determined by the user of the system or automated determination of the central programming device.

In some examples, a central programming device (“CPD”); may implement one or more of the following capabilities:

-   -   (a) access and use of a library of known exploits that target:         digital devices; computing devices; networked computing devices;         files or applications used or stored on computing and/or digital         devices or operating systems or other architecture features of         digital system that are intended to provide information on known         attempts to breach a computing device or files/records/function         resident or under control of digital device(s);     -   (b) compare library data with a set of actions collected or         under real time observation to determine common element(s);     -   (c) access a library of known countermeasure(s);     -   (d) may select and apply countermeasure(s);     -   (e) may measure the effectiveness of countermeasure(s);     -   (f) may establish a threat level measure for factors that         indicate a change in the threat environment;     -   (g) may determine whether the threat was to the central         programming device;     -   (h) may determine if the threat was to a linked device;     -   (i) may determine if the threat was to a non-linked device;     -   (j) may collect data on the log, and other data retention         components;     -   (k) may store data on internal logs;     -   (l) may change rules and/or trust level of device(s), file(s),         application(s) or any combination thereof;     -   (m) may alert other central programing device(s) of incident and         countermeasure effectiveness at any point in the incident with a         high priority of notice if system or system asset if         compromised;     -   (n) may restrict, change, limit or eliminate device(s), file(s),         function(s) or application(s) that may be the source of         threat(s);     -   (o) may query other central program device network(s) for         library data on a specific of behaviors;     -   (p) may receive queries from other central programming devices         for library data;     -   (q) may reply to other central programming device queries with         affirmative information requested;     -   (r) may reply with no information or a communication to central         program device source of query that no information is found;     -   (s) may sever communication with a central programming device or         linked device based upon rules, protocols or policies;     -   (t) may field and dispatch quickly any future queries on the         same topic from the same central programming device or other         central programming devices;     -   (u) may mount defense against a denial of service attack or         other threat posed by another central programming device(s) or a         linked digital device;¹         -   a. may engage linked devices in digital environmental             surveillance; ¹ Here, one might analogize a person's blood             stream to the wireless communication environment in the             sense of the immune system mounting a defense to an invasion             traveling in the bloodstream from an adverse element in the             organic system.         -   b. may assign roles to linked devices base on their purpose             and roles assigned to report on active communications sent             and received;         -   c. may task linked devices to collect data;         -   d. may task linked devices to store data;         -   e. may task linked devices to transmit data;         -   f. may task linked devices to report data to other linked             devices;         -   g. may assign linked devices with task to continuously             monitor the environment for wireless communication;             -   i. may task a device to monitor the environment and                 communicate if attempts are made to access certain                 functions or application;         -   h. may assign values to the functions and applications of a             device and determinants for specific actions to measure a             threat         -   i. may task linked devices with communication monitoring             rules;         -   j. may instruct linked devices to prohibit communication             from one or more devices;         -   k. may severe links with devices;         -   l. may prohibit communication among one or more linked             devices;         -   m. may assign collaborations among linked devices;         -   n. may assign work tasks among one or more linked devices;         -   o. may alert other central programming devices about the             behavior of a linked device that is counter to its purpose,             classification, or assignment role.     -   (v) may communicate threatening behavior by a linked device or         other central programming device to other related central         programming devices;     -   (w) may engage in automated decision making regarding network         resources and processes allocation of functions;     -   (x) may prioritize allocation of resources that comprise a         linked network to meet over objectives as outlined by emergency         protocols or rules for network operations a risk to overall         operations or performance of tasks of linked devices;     -   (y) may develop new security applications to inform rules for         devices, central programming devices, applications, file         management, allocation of resources or any combination thereof         based upon exiting and learned behavior.

In some examples, the central programming device may manage a plurality of wireless-enabled devices or other central programming devices capable of wireless communication with the CPD or each other;

-   -   (a) may maintain a record of unique identification for each         linked device for communication and/or security management;     -   (b) may tag each device upon initial enrollment as being a         member of a unique linked group of devices;         -   a. may assign levels of trust among devices of a similar or             dissimilar type;         -   b. may create rules for devices;             -   i. may assign digital traffic monitoring of a particular                 type base upon the type of device a rule is developed                 for;             -   ii. may engage in passive data traffic monitoring                 without retaining data;             -   iii. may monitor how wires device engage the fog                 security network;             -   iv. may tag an intruder device base upon its engagement                 with the fog security network on engagement that                 increased threat awareness         -   c. may tag operating files, applications, directories as             being assigned to a unique device or group of devices;         -   d. tags may be interactive (capable of reporting status upon             initialization by an operating system, engagement by a             process, commands sent or received, when accessed, when             used, change of state, file size, or any combination             thereof;         -   e. tags may be passive to allow verification upon request             that may use rules, protocols, policies or procedures that             authenticate the central programming device before complying             with request;         -   f. tags may provide one function authentication of its             origin;     -   (c) may access a directory of known central programming devices         or linked devices that may include identifiers for such devices         such as their IMEI, MAC address, log of recent activity or other         information intended to authenticate a communication from a         central programming device or linked device as well as         authenticate the identity of a source or destination for a         communication that reaches a central programming device or         linked device;     -   (d) may use block chain or method with the same intent of         increasing trustworthiness of a method of accurately         authenticating a device(s), application(s), network(s), or         central programming device(s) may provide support of the defense         of central programming device;     -   (e) may automate processes that create gatekeeping functions for         communication among linked devices that forward communication         received from a central programming device to another central         programming device or to linked device(s) that are intended to         route the message securely through a trusted subnet of central         programming devices device or linked device(s) to an end user;     -   (f) may automate processes to allow two-way communication among         linked devices to facilitate operation or processing of services         to prevent disruption due to a threat or disabling of critical         services;     -   (g) may forward the original message received from a central         programming device;     -   (h) may use rules to assign roles for linked devices that are         specific to the needs of the fog security network;

Device(s) assigned to the fog security network may mimic other wireless device wireless communication characteristics;

-   -   (a) Device(s) may monitor select files or all files and folders         on a designated or linked device(s)     -   (b) Device(s) may monitor use of some or all firmware components         s of a linked device     -   (c) Device(s) may monitor service or support devices that are         used by components of a fog security network (printers, copiers,         use of network resources)     -   (d) Devices may report activity of devices monitored;     -   (e) Devices may report activity of non-monitored devices;     -   (f) Devices may record routine activity of members of the linked         network for determination of healthy states of activity based on         time of day, day of the week, month of the year, department,         office, device, user or other factors that would indicate what         is routine;     -   (g) Devices may store data regarding monitored devices     -   (h) Devices may transmit threat signature data or activity data,         but not necessarily user identifiable information or proprietary         data stored, used or managed by the user of a devices;     -   (i) Devices may record data on linked or monitored devices;     -   (j) Devices may work independently, in concert, parallel,         sequentially or any combination thereof;     -   (k) Devices may have protocols that allow communication with         other central programming devices should security rules allow     -   (l) Device may adjust data flow from a device;     -   (m) Device may adjust data flow to a device;     -   (n) Device may detect anomalous or prohibited behavior of a         linked or monitored device;     -   (o) Device may detect attempt to access prohibited files or         records;     -   (p) Device may detect anomalous device activity;     -   (q) Device may access monitored device file use and activity         history;     -   (r) Device may limit flow of data from a device.

In some examples, a central programming device may be leveraged to prevent loss or theft of physical objects. We refer to these systems and methods below as “Never Lose It” as a shorthand moniker. The Never Lose It—will save time, money, worry, and hassle by preventing the loss of portable items before it happens. A hat left on a train, an umbrella on a bus, a book in a hotel room, keys or a phone lost at airport security screening as you gathered your belongings rushing to get to your departure gate.

This is a mobile technology loss and theft prevention communication system that uses networking protocols. It is comprised of a central programming device (CPD), which may be provisioned, for example, on a smartphone, laptop, computer automobile, etc., to send and receive wireless signals from IoT devices. CPD must register, at users' control or pre-set automated command: other CPDs or IoT items; proximity distance preferences; alert format—including accessibly options; set a time/duration for loss prevention; and perform additional actions as indicated by user, which can include use of a pin to suspend or extend a loss prevention session.

An application on CPD will manage data sent and received from IoT devices to measure distance of each enrolled item from the CPD. Communicate unique IoT data regarding each stationary or mobile item(s) to the CPD. The CPD may collect or use stored device stored biometric(s) on the user as a secondary measure to authenticate the user. Alerts can be recorded in the user's voice; use vibration or visual alerts to support accessibility, or select from a list of pre-recorded images or sounds to identify item(s) should proximity rule be violated. In an embodiment, CPD calculates distance of each item and sends alerts when a proximity rule is violated. CPD may host proximity rule for its own loss prevention that may linked to the proximity of an enrolled item or secondary item.

The CPD in some embodiments may provide secondary item specific alerts automatically to telecommunication service providers, home security services, financial service providers, automobile theft or road side assistance services, etc. when a loss occurs based on the preference of the user. If a secondary alert item is recovered a reminder to contact vendors can be given to users to provide and update on the status of a recovered item.

Preventing loss before it occurs has not been done. There are products that find something after it is lost, but this only works if you have an idea where the loss occurred and can return to that location. Another approach is to have a smart tag on the item that may be lost and hope it is used to contact the owner. To illustrate, imagine a hat left on a train, an umbrella on a bus, a book in a hotel room, keys or a smartphone lost at airport security as you gathered your belongings rushing to get to your departure gate. In accordance with embodiments of this disclosure, a user can be alerted when he is about to leave something behind, and given enough time to retrieve it instead of discovering the loss after it was too late to prevent it.

In other embodiments, the Never Lose It provides users with the ability to use a wireless smart tag technology affixed to non-IoT objects (bag, backpack, purse, wallet, umbrellas, books, keys, hats, scarfs, gloves, etc.) and link them to a smartphone based upon proximity as described in detail above. If the corresponding proximity rule is broken, then an alert may be issued so the owner can retrieve the item before it is lost. Alerts may be transmitted in many ways; for example, by text message, audio or visual alerts, email, vibration, etc. just to name a few.

The Never Lose It—is simple to use. It requires that users only know how to use a smartphone or equivalent device. Other devices may be used as well with appropriate programming and communications capabilities. One added benefit is not need having to give personal information to strangers in hopes that they will return the item. The best option for lost prevention is using the Never Lose It App on a smart IoT device.

It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the invention. 

The invention claimed is:
 1. A wireless communication system to prevent loss or theft of physical items, the system comprising: a central programming device (“CPD”) having a user interface; and at least one wireless-enabled device capable of wireless communication with the CPD; the CPD including a processing device and a memory device having instructions stored thereon, wherein the instructions, in response to execution by the processing device, cause the CPD to: responsive to input via the user interface or preset preferences, identify and register the wireless-enabled device at the CPD as a registered device, the register step including acquiring an IP address of the registered device; establish at least one operating rule for the registered device, responsive to user control or preset preferences, the operating rules including a proximity rule; responsive to input via the user interface or preset preferences, establish a distance value for the proximity rule; responsive to input via the user interface or preset preferences, set an alert format for the registered device; responsive to input via the user interface or preset preferences, set a time parameter rule for the registered device; commence a loss prevention session using wireless communications between the CPD and the registered device; during the loss prevention session, monitor a current distance of the registered device from the CPD, based on data sent to and received from the registered device; and based on a violation of the proximity rule combined with the time parameter rule, conditionally activating an alert using the set alert format.
 2. The system of claim 1 wherein the stored instructions, in response to execution by the processing device, further cause the CPD to perform additional actions responsive to input by the user interface.
 3. The system of claim 2 wherein the additional actions include use of a PIN input to the user interface to suspend or extend the loss prevention session.
 4. The system of claim 1 wherein the stored instructions, in response to execution by the processing device, further cause the CPD to collect or use stored biometric data to authenticate a user as a condition to commencing or modifying or suspending a monitoring session.
 5. The system of claim 1 wherein the stored alerts comprise audio alerts pre-recorded in the user's voice.
 6. The system of claim 1 wherein the stored alerts comprise vibration or visual alerts to support accessibility.
 7. The system of claim 1 wherein the stored alerts include a plurality of pre-recorded images or sounds, each to identify a corresponding registered device when the alert is activated.
 8. The system of claim 1 wherein the stored instructions, in response to execution by the processing device, further cause the CPD to provide secondary, registered device-specific alerts automatically to a telecommunication service provider.
 9. The system of claim 1 wherein the stored instructions, in response to execution by the processing device, further cause the CPD to provide secondary, registered device specific alerts automatically to at least one of home security services, financial service providers, automobile theft or road side assistance services, when a loss of a registered device occurs based on the preference of the user.
 10. A wireless communication system to prevent loss or theft of physical items, the system comprising: a central programming device (“CPD”) having a user interface; and at least one wireless-enabled device capable of wireless communication with the CPD; the CPD including a processing device and a memory device having instructions stored thereon, wherein the instructions, in response to execution by the processing device, cause the CPD to: responsive to input via the user interface or preset preferences, identify and register the wireless-enabled device at the CPD as a registered device, the register step including acquiring an IP address of the registered device; establish at least one operating rule for the registered device, responsive to user control or preset preferences, the operating rules including a proximity rule; responsive to input via the user interface or preset preferences, establish a distance value for the proximity rule; responsive to input via the user interface or preset preferences, set an alert format for the registered device; responsive to input via the user interface or preset preferences, set a time parameter rule for the registered device; commence a loss prevention session using wireless communications between the CPD and the registered device; during the loss prevention session, monitor a current distance of the registered device from the CPD, based on data sent to and received from the registered device; and based on a violation of the proximity rule combined with the time parameter rule, conditionally activating an alert using the set alert format; wherein the registered device comprises a wearable device arranged to be wearable by or attached to a child, and a parent or guardian of the child is an authorized user of the CPD to set the proximity and time rules.
 11. The system of claim 10 wherein the wearable registered device includes a user interface to alert a wearer; and the CPD is configured to notify the wearable registered device to activate an alert via the user interface of the wearable registered device responsive to a violation of the proximity rule.
 12. The system of claim 11 wherein the user interface of the wearable registered device includes a display screen to display an animated character as an avatar to engage a child wearer responsive to the violation of the proximity rule.
 13. The system of claim 10 wherein the wearable registered device is configured to transmit a message to the CPD responsive to a wrist band of the wearable registered device being broken or removed. 